/customer
[GET]
This usecase is to retrieve customer details based on identity proof.
URL
https://[host]:[port]/emida-ux/v1/{businessId}/customer
URI Params
| name | type | description | required |
|---|
| businessId | string | Default CR for Costa Rica | Y |
| name | type | description | required |
|---|
| client_id | string | The client_id identifying the channel. Minimum characters: 5 | Y |
| client_secret | string | Password associated with the client_id. Minimum characters: 5 | Y |
| X-Correlation-ID | string | Identifier that correlates HTTP request between a client and server.
Any identification model (UUDI, checksum, etc.) can be used, as long as it is a unique value to differentiate a transaction. | Y |
Query Param
| name | type | description | required |
|---|
| engagedParty.individualIdentification.identificationId | string | Unique Identifier of Identification Type. | Y |
| engagedParty.individualIdentification.identificationType | string | Expected values are: ID Card, Legal ID, Resident ID, Passport, TIM and Others. | Y |
cURL Request
curl --location 'https://nonprod.lcr.esb.cloud.lla.com/test/emida-ux-lcr/emida-ux/v1/CR/customer?engagedParty.individualIdentification.identificationId=484239892&engagedParty.individualIdentification.identificationType=passport' \
--header 'X-Correlation-ID: {{$guid}}' \
--header 'client_secret: ******' \
--header 'client_id: ******'
Response
[ {
"id": "1234",
"name": "JUAN CARLOS PEREZ GONZALEZ",
"status": "active",
"account": [
{
"id": "1079301",
"@type": "BillingAccount"
}
],
"contactMedium": [
{
"mediumType": "email",
"characteristic": {
"emailAddress": "someeamil@gmail.com"
}
},
{
"mediumType": "Telephone",
"characteristic": {
"phoneNumber": "5555555555"
}
}
],
"engagedParty": [
{
"@referredType": "Individual",
"id": "1234",
"role": "Customer",
"name": "JUAN CARLOS PEREZ GONZALEZ",
"individualIdentification": [
{
"identificationType": "passport",
"identificationId": "900770050"
}
]
}
],
"@type": "Customer"
}]